with over 300 actions which more can be added by the SySop
18. Sophisticated Node Control Module
19. Online Messaging between users w/Multi-Nodes
20. Parser commands for use in text files and Online programs
17. Much Much More...
1.3 Registration of Trinity BBS
As a non-registered SYSOP of Trinity BBS, you many copy, use, and run
the BBS for a short time period. During this period you can decide if you
would like to register as a Trinity BBS SYSOP. Un-registered copies of BBS
are identical to registered copies except there is a40 user limit for the
BBS. Which means only 40 new users are accepted. After you reach this 40
user limit you should register your copy. To register Trinity BBS, fill
out the registration sheet (REGSHEET) or include the information on the
sheet on a seperate piece of paper and send the shareware registration fee
of $49.95 to :
Trinity BBS
c/o Rodney Martin
5501 Northcutt PL
Dayton, OH 45414
USA
(513)890-5204 Trinity BBS Headquarters
email: rmartin@pmci.com
Please send checks or money orders only and make them payable to Rodney
Martin. International users must use US International money orders.
After being a registered SYSOP you will have the right to receive updates
of the BBS via Trinity Headquarters BBS or U.S. mail. Downloading updates
is free but there is a $5 shipping and handling charge for U.S. Mail.
The complete Trinity BBS source code can also be purchased for $395.95.
1.4 Un-registered Versions
UN-REGISTERED versions of this BBS may be freely distributed and
encourage to do so. This program may be distributed via any distribution
service as long as the distribution fee is under $5 per disk. Please by
pass the restrictions on registered versions. These restrictions do not
apply for un-registered versions.
1.5 Registered Versions
REGISTERED versions of this program can only be used on a single computer
at a time. You may not distribute registered copies of the program to others.
You may modify or translate the program for personal use only, and only in
accordance with all other parts of this agreement, unless prior written
permission has been given by the author stateing otherwise.
YOU MANY NOT USE, COPY, MODIFY, OR TRANSFER THE PROGRAM, DOCUMENTATION, OR
ANY OTHER COPY, EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT.
You may make copies of REGISTERED versions of the program for back-up
purposes only. You must reproduce and include the orginal copyright notice
on the back-up copy. You may transfer the original product to another
party if the other party completes and returns a registration sheet to the
author and stateing the transfer agreement. If you transfer the program,
you must at the same time transfer all back-ups to the other party.
1.6 Copyright
The program and its related documentation are copyrighted. You may
only copy and distribute UN-REGISTERED versions of the program. REGISTERED
versions may not be copied except for back-up purposes and to load the
program into the computer as part of executing the program. All other
copies of the program and its documentation are in violation of this
agreement.
YOU MAY NOT REMOVE THE COPYRIGHT NOTICES AT ANY TIME.
1.7 Program Warranty
The author of this software warrants the disk on which the program is
furnished to be free from defects in materials and workmanship under normal
use for a period of 90 days from the date of delivery to you as evidence by
the shipping records. To obtain a warranty service or replacement, you
must deliver the defective unit prepaid to the author.
EXCEPT TO THE EXTENT PROHIBITED BY APPLICABLE LAW, ANY IMPLIED WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE ON THE DISK IS LIMITED
IN DURATION TO THE DURATION OF THIS LIMITED WARRANTY.
The program and its documentation (software) are provided "as is"
without warranty of any kind, either expressed or implied, including but
not limited to the implied warranties of merchantability and fitness for a
particular purpose. Should the program or documentation prove defective,
you (and not the author, dealer, distributer, or representative) must
assume the entire cost of all necessary servicing or repair. Further, the
author does not warrant, guarantee, or make any representations regarding
the use of quality, correctness, accuracy, reliability, currentness, or
otherwise, and you rely on the program and results solely at your own risk.
The author does not warrant that the program or documentation will
meet your requirements or that the operation of the program will be
uninterrupted or error free.
1.8 Update And Customer Support Policy
In order to be able to obtain any customer support or updates of this
program, you must be a registered SYSOP. If the author is aware of breech
of any part of the REGISTERED SYSOP agreement by you, he is under no
obligation to make available to you any customer support or updates to the
program.
Updates and Customer Support may be obtained on The Trinity BBS
Headquarters(4 Nodes) at 513 890-5804 or 513 890-6992 24hrs a day,
7 days a week, and 1200-28.8 Bps.
1.9 Acknowledgement
You acknowledge that you have read this agreement, understand it, and
agree to be bound by its terms and conditions by signing and mailing the
enclosed registration sheet and registration shareware fee. You also agree
that this agreement is the complete and exclusive statement of prior
agreements between the parties and supercedes all proposals or prior
agreements, verbal or written, and any other communications between the
parties relating to the subject matter of this agreement.
Should you have any questions concerning this agreement, please
contact the author in writing.
PART 2 HARDWARE CONFIGURATION
This section will assist you in choosing the correct computer
equipment for use with Trinity BBS. You shouldn't have many-if any
problems with devices connected to your Amiga computer.
2.1 Computers
Trinity BBS will correctly run on all current models of the Amiga
computer, including the A1200 and A4000. Trinity BBS was designed under
Amige OS V2.04. It has been tested with V2.1 and should work correctly
with all versions of the OS from 1.3 to 3.x. However, there is no guarantee
that future versions will be compatible with older versions of the OS.
2.2 Modems
Trinity BBS uses the Hayes compatible AT (attention) command set. You
must use a modem that supports this command set. Any baud rate will work
with this BBS. Version 2.0 now uses seperate modem configration files and
can be configured for vertially any modem. (See Modem Configuration)
2.3 Disk Drives
As of Version 2.0, Trinity BBS requires at least a 20 Meg hard drive.
Large drives is obviously recemmend for file libraries. Trinity BBS will
take complete advantage of CD-ROM drives.
2.4 Memory Requirements
Trinity BBS requires at least 2 MEG of memory for a one node system.
Aproximatly 512 more kbytes is required for each addtion node. Large AREXX
Online Programs will require may require even more ram. For an example a 6
Meg Amiga should handle 4 nodes.
2.5 Micro-Processor And Enhancer Boards
Trinity BBS should work with all current Micro-Processor chips and
Enhancer boards. When running multi-nodes, it is wise to use a faster
micro-processor, expecially with heavy multi-tasking. For an example an
Amiga 3000 with a 25mhz 68030 handled 4 nodes respectively and a 68040
equiped A4000 should handle 16 nodes respectively with use of Trinity.
PART 3 INSTALLING TRINITY BBS V2.0
The primary goal you must think about when first setting up your BBS
is to set it up so that it fits your needs and interests. Trinity BBS can
be customized anyway you as the SYSOP would like it to be. You will need a
text file editor and/or an ANSI text editor, such as Qed and Ansi Master.
This documentation expects that you have an average knowledge of Amiga Dos.
If you do not, please study the Amiga Dos manual before continuing.
3.1 Upgrading From A Previous Version Of Trinity BBS.
Please refer to the file "UPDATE.README" for instructions on updating
your current version of Trinity BBS. This file will explain how to update
as well as the new features of the update.
3.2 Installing Trinity BBS V2.0
To install Trinity BBS V2.0 please run the program "INSTALLHD" and
follow the on screen instructions as well as answer all questions. This
program will install V2.0 to your hard drive.
After installation you may have to edit the "BOOTBBS" script that the
install program will create for you. This installation script is required
to make all assignments to the directorys. The Install program will include
comments in the script. Please examine this file and edit where needed.
You may edit your "S:USER-STARTUP" script to automaticly execute your "BOOTBBS"
script during a reboot.
Example BootBBS Script :
##
;40000 is a required stack size for each Trinity BBS V2.0 Node.
C:STACK 40000
;
;Fast Fonts Program required for force IBM8.font for each node
;However on OS 3.x this may fail or crash. If so you must force the IBM8.font
;into the shell that will load Trinity BBS to output IBM ansii characters
C:FF IBM8.Font
;
;Arexx should be started in the "S:STARTUP-SEQUENCE", remove comment is needed
;C:REXXMAST
;
;The following devices should be mounted in your "S:USER-STARTUP" by default
;but if not remove the ";" before each
;C:MOUNT AUX ;Mount Aux Device
;C:MOUNT PIPE ;Mount Pipe Device
C:ASSIGN T: RAM:
;
;The following assignment is the root path location of TrinityBBS and it's
;main files
C:ASSIGN TRINITY: DH0:trinitybbs
;
;The following assignments may be assigned to any device and path
C:ASSIGN MSGAREA: TRINITY:msgarea
C:ASSIGN FILEAREA: TRINITY:filearea
C:ASSIGN EMAIL: TRINITY:email
C:ASSIGN NEWS: TRINITY:news
C:ASSIGN CONFIGURATION: TRINITY:configuration
C:ASSIGN BULLETINS: TRINITY:bulletins
C:ASSIGN OLP: TRINITY:olp
C:ASSIGN USERLOG: TRINITY:userlog
C:ASSIGN TEXT: TRINITY:text
C:ASSIGN PLINE: TRINITY:pline
C:ASSIGN LOGS: TRINITY:logs
;
;The following will actually boot the BBS
;You may wish to put these in a seperate script
;so you can make the required assignments but
;not actually boot the BBS - usefull for configuration
;and or updating versions
C:RUN TrinityControl -s
C:RUN TrinityBBS 1 -i
;Each Addtional Node would follow, for an example
;C:RUN TrinityBBS 2 -i
;And for the SySop only node
;C:RUN TrinityBBS 0 -i
;Control and Nodes may be run seperatly from cli/shell prompt as well
##
The reason I used assign devices instead of just plain path locations
is because this way it is easier for you to transfer an area or directory
to a different device. All you would have to do is copied the require path
onto the new device and change the new assignment without having to worry
about changing a large configuration every time.
3.3 Installed Sample Setup
The inital installation process will create a complete sample setup for
you to examine the BBS. This setup will consist of 3 users, the first user
(account #1) with a handle of SYSOP and a password of TRINITY, 3 message areas,
and 2 file libraries with 5 file areas in the first library and 3 libraries in
the second, 1 bulletin file, and 1 online game. Feel free to take a tour of
this setup to get aquainted with the way Trinity BBS operates before
continuing to configure your own BBS.
PART 4 The Trinity BBS Configuration Utility
Inclosed in the Trinity BBS package is a configuration program called
"TrinityUtility." After executing your Boot script run TrinityUtility.
This program will check and see if you have a configuration already
created, if so it will load it into memory, otherwise it will be set to the
defualt configration. This opening menu will consist of several options to
configure your BBS as well as reset certain areas (which you must do to
remove the demonstration setup). Here is a description of each option:
Option 1: Edit Main Configuration
This option will allow you to setup your main configuration file. If a
main configuration file is found it will load it into memory and allow you
to edit the fields otherwise it will load in preset defaults. (See Section
3.5: Main Configuration)
Option 2: Edit Node Configuration
This option will allow you to setup each individual node's configuration
including node 0. If a configuration is found for a given node it will be
loaded into memory otherwise preset defaults will be loaded. (See Section
3.5: Node Configuration)
Option 3: Reset Userlog
This option will reset the userlog directory to zero users. Warning:
this will completely wipe your userlog files and should only be used during
the initial setup of your BBS. However, if your userlog should ever become
corrupt this is the only automatic meansw of re-initializing your userlog.
Option 4: Reset Message Areas
This option will completely reset your msgarea: directory. Warning:
this will completely delete all message areas and messages posted and should
only be needed to during the initial setup of your BBS. However, if your
message areas should ever become corrupt this is the only automatic means of
re-initializing your message areas.
Option 5: Reset File Areas
This option will completely reset your filearea: directory. Warning:
this will completely delete all file areas and files uploaded and should
only be needed to during the initial setup of your BBS. However, if your
file areas should ever become corrupt this is the only automatic means of
re-initializing your file areas.
Option 6: Reset E-Mail Area
This option will completely reset your email: directory. Warning:
this will completely delete all E-mail messages and uploaded email files
and should only be needed to during the initial setup of your BBS. However,
if your file areas should ever become corrupt this is the only automatic
means of re-initializing your E-mail areas.
Option 7: Reset Partyline
This option will completely reset all partyline user configuration
files. All users will have to re-create their partyline configurations.
4.1 Main Configuration
The main configuration holds the global configuration for all nodes.
You must fill out each field before saving the main configuration file. The
fields are described as follows:
BBS NAME :
Enter the name you would like to call your BBS.
SYSOP's NAME :
This is the handle of the SYSOP. All feedback will go to the Email
location of this handle. So you must use this handle as the handle
the SYSOP will use on the BBS.
TOTAL NODES :
Enter the total number of nodes (number of phone lines) you will be
using on your BBS. Note the more nodes you have the more RAM you will
need. Also, Node 0 is not included in this list since it is a local
node only. For a one phone line BBS enter a 1.
USER DELETE MONTHS :
Enter the number of months you would like auto-maintenance to delete
users who have been in-active (haven't called) with in this time frame.
Enter '0' to disable this function (never delete users).
PARTICIPATION CREDTIS:
These are awarded to users when they post and/or reply to public
messages.
FREE OLP CREDITS :
This is the amount of Online Program Credits a user receives for every
80 character line of a message he/she writes a message.
FREE DOWNLOAD CREDITS :
This is the amount of Download Credits a user receives for every 80
character line of a message he/she writes.
ALLOW NEW USERS :
If this is set to YES, the BBS will accept new user log ons.
Note it is auto-maticly set to NO when an unregistered BBS already
has 40 users.
SYSTEM/ENVIRONMENT DEFAULTS:
This are the defaults the BBS will use for a certain action, most can
be toggled as a menu item on the each node's screen either YES or NO.
SYSOP IN :
If this is set to YES, the BBS will page the SYSOP otherwise it will
tell the user that the SYSOP is unavailble and will allow the user to
leave feedback.
UD AREA CLOSED :
If this is set to YES, the BBS will not allow any user to enter the
file areas.
MSG AREA CLOSED :
If this is set to YES, the BBS will not allow any user to enter the
message areas.
OLP AREA CLOSED :
If this is set to YES, the BBS will not allow any user to enter the
Online Programs Section.
SPEECH ON :
If this is set to YES, the BBS will announce all user logins using
the Amiga's built in speech device.
LOGS:
Logs are files located in the "LOGS:" directory that the BBS can
write real time activity. Logs may use quite a bit of hard drive space,
so you might not want to have all logs turned on. In this section you
can state which, if any, logs you would like turned on. A setting of YES
will tell Trinity that you wish to have that option logged.
CALLER LOG :
The caller log will show all user logins and logoffs. During login it
will write that the user has logged in on the current date and time.
During logoff it will write that the user did logoff on the current date
and time as well as the users account number, real name, phone number,
total chat pages, total email sent, total messages posted, total
downloads, and total uploads. This log file is also the log file used
by the AREXX command SENDLOG {output}. The path/filename of this log
file is "LOGS:CALLER.LOG".
UPLOAD LOG :
The upload log file will show each upload users make, include adopting
files by SySops. The log record will state the filename, current date and
time, and the area the upload was made. The path/filename of this log file
is "LOGS:UPLOAD.LOG".
DOWNLOAD LOG :
The download log file will show each download users make. The log
record will state the filename, current date and time, and the area the
download was made. The path/filename of this log file is "LOGS:DOWNLOAD.LOG".
MAINTENANCE LOG :
The maintenace log file will show what the auto maintenance program did
during maintenance time. It will state the date and time, what users were
auto deleted, what messages w/areas were deleted, and what files w/areas were
deleted. The path/filename of this log file is "LOGS:MAINTENANCE.LOG".
OLM LOG :
The OLM (Online Messages) log file is used for capturing all OLMS that
users send to each other in a multi-node environment (See section x.x: Online
Messsages). This log file will quickly grow large in size if not reset often.
The path/filename of this log file is "LOGS:OLM.LOG".
PARTYLINE LOG :
The partyline log file will capture all output from the partyline (See
section x.x: The Partyline), including all private/broadcast messages and
actions. This log file will also quickly grow large in size if not reset
often. The path/filename of this log file is "LOGS:PARTYLINE.LOG".
After you have answered all of these questions, select '2' to save your
new main configuration and '2' to quit back to the main options menu.
4.2 Node Configuration
The node configuration section allows you to setup each individual node
including node 0 (The local only node). Each node requires it's own serial
device to use. Even though node 0 does not use the serial port at all, it
will still need the serial/modem fields defined. You must fill out each
field before saving each node's configuration. The fields are described as
follows:
NODE NUMBER :
Enter the node number you wish to edit. If the node's configration
exists it will auto-load all fields as stored, otherwise it will load
defaults. You must edit all nodes, including node 0, that you will be
running.
SERIAL DEVICE :
Enter the name of the serial device you wish to use for this Node.
For the internal serial device, you would enter "serial.device".
Multi-serial cards, internal modems, or special network serial devices
(telser.device, for example) will have their own serial device, please
please contact your serial card manual for the appropriate device to
use.
SERIAL DEVICE UNIT :
Enter the device unit for the serial.device you are going to use. For
the internal serial.device and an external modem, you would enter "0".
Multi-serial cards, internal modems, or special internet serial devices
will have their own unit configuration.
MODEM CONFIG FILE :
New to version 2.0, Trinity uses special modem configuration files that
hold init strings and result codes for modems. These modem configuration
files must be located in the "CONFIGURATION:" directory, along side all
main and node configuration files. The filename for a modem configuration
can be anything, but I used a standard of "MODEMNAME.MODEM". You may
have to create your own configuration for your modem. (See section x.x:
Modem Configuration). Enter the filename of modem configuration file in
this field. Note, the path CONFIGURATION: is not needed with the
filename.
PORT BAUD RATE :
Enter the baud rate you would like your Amiga to talk to the modem. If
you are using a 9600 baud or higher modem you would use 19200 for the
internal serial.device. However, for faster serial devices and modems
you may use 38400 or above. The maximum speed is 115200. If you are
using a modem with a max baud of 2400 or below you must enter the max
baud rate the modem supports, for example 2400.
SCREEN COLORS :
This is the total number of screen colors you would like to be used on
this node. The lower the number the smoother and faster the node will
operate. Valid values are 2,4,8,16. If you select 4 or less colors you
may see colors collide, especially with multi-colored ANSI text.
SCREEN TYPE :
You may tell Trinity how to open the screen for this node. The availbe
types are Default (640x200), Use WorkBench, or Custome. If you select
default the screen will use the Amiga's default screen size. If you
select use workbench, Trinity will look up your workbench screen settings
and will build the screen to match (Note, if your workbench is in inter-
lace you must tell Trinity to use interlace as well, otherwise the screen
will not fit completely in non-interlaced mode. If you select custome you
must define the screen size, however; if you give invalid screen sizes the
node will more than likely crash during bootup. You can be very creative
will screen sizes allowing it to be possible to use small screen rows to
be able to overlay two nodes output on your monitor at one time. This is
a very nice feature.
INTERLACED? :
If you would like this node to open up in interlaced mode as a defualt,
select 'YES' to this flag. This is required if you choose use workbench
as the screen type and your workbench screen is in interlaced mode.
MIN BAUD TO LOGON :
Enter the minimum baud rate you would like to require to login this node.
MIN BAUD TO DOWNLOAD :
Enter the minimum aud rate you would like to require for downloading on
this node.
MIN BAUD TO UPLOAD :
Enter the minimum aud rate you would like to require for uploading on
this node.
After you have answered all of these questions, select '2' to save your
new configuration for this node, you may now edit configurations for other
nodes by changing the node field or '2' to quit back to the main options menu.
3.5 Auto Maintenance Time Configuration
In versions of Trinity BBS before 1.8, auto maintenance was always
forced to be run at midnight. In later versions, including version 2.0, a new configuration file was created called "CONFIGURATION:MAINTENANCE.CONFIG".
This file holds the 24hr format of the time you would like your auto maintenace
to be ran. The default is 5am, you may change this to any time you would like.
3.6 Modem Configuration Files
Version 2.0 now uses special modem configuration files for init strings,
response codes, ect... for easy configuration of different modem types.
Included in version 2.0 of the archive are sample configurations for
USRsportster modems as well as default configurations that can be edited for
other modems. These configuration files must be located in the "CONFIGURATION:
directory and included in the node config file of the node the modem is to be
used. If you need to create a new configuration file for a new modem, copy
the one of default configuration files, that matches close enough to the
highest baud rate of the new modem, to a new filename of your choice and edit
this file. The comments in the file should help you adjust any parameters.
You must keep in mind that Trinity requires that echo commands be set off,
responce to DTR set on, connection speed must respond to remote speed (not
the port speed), carrier detection set to on, cts/rts handshaking, and
numeric responce codes only.
PART 4 EDITING TEXT FILES
Trinity BBS uses several different text files including, menu files,
logon/logoff files, new user files, intros, ect. You may use any text
editor or Ansi editor for creating or editing these files. I recemmend Ced
and Ansi Master for editing text files. The format for most text files is
as follows :
FILENAME.Ttcc.Aaa
Filename is the name of the text file, LOGIN for example. The .T is the
terminal and column number of the current user. "t" is either 1 for ASCII
or 2 for ANSI depending on the type of terminal the user is using. "cc"
stands for the total columns or characters the user has on his terminal
screen it will be either 40 or 80 columns. The ".Aaa" is an optional
access level requirement to view the text file. You can create several
different versions of a text file for each access level.
Example : LOGIN.T280 = Text file LOGIN for a user with ANSI and 80
columns.
LOGOFF.T140 = Text file LOGOFF for a user with only ASCII
and 40 columns.
If the BBS can not find a text file with the correct terminal
specifications it will try to locate the default which is T280 (ANSI 80
columns). You may also add an access level restriction to the file which
is an extention of ".Aaa" to the filename.
Example : LOGIN.T280.A10
If a user with an access level of 10 and only 10, the text file
will be displayed with a .A10 extention. Note : you must add this
extention to all terminal extentions of the file so all users with that
access level with any terminal specification will be able view the same file.
Examples : WELCOME.T280.A10
WELCOME.T240.A10
WELCOME.T180.A10
4.1 Files In The Text Directory
You must create or edit the following files that are located in the
text directory : Note, they all most have a terminal specification extention
".Ttcc" and, but not required, an access level extention ".Aaa".
LOGIN
This file will be displayed as soon as someone logins before the
account number or username prompt.
WELCOME
This file will be displayed when someone completely logs in by
either as a new user or by correctly entering username/account
number and password.
LOGOFF
This file will be displayed when a user logs off or is forced off
the system.
NEWUSER
This file will be displayed when a new user calls.
MAINMENU
This is the Main Menu Text File. It will display all the
available commands for the Main Menu.
MSGMENU
This is the Message Area Menu Text File. It will display all the
available commands for the Message Areas.
FILEMENU
This is the File Area Menu Text File. It will display all the
available commands for the File Areas.
EMAILMENU
This is the E-Mail Area Menu Text File. It will display all the
available commands for the E-Mail Area.
SYSOPMENU
This is the SYSOP Options Text File. It will display all the
available commands for the SYSOP Options.
HELP-EDITOR
This file will be displayed when a user issues "?" while using
the message text editor.
ACTIONLIST
This file will be displayed when a user wants to list available
actions in the partyline. You MUST create this file before they
will know what actions are available to use. You can create
secret actions and not include them on this list. As long as the
action exists in your "PLINE:ACTIONS" directory, that action can
still be used as long as you know the name.
4.2 Intro Text Files
There are several areas of the BBS that offer Intros. This Intros are
text files that will be displayed when a user enters a certain message
area, file area, OLP area, ect. They are to be edited the same way any
other text file is to be editing including all extentions. Not Intros are
not required to be created/edited. They just spice up areas of the BBS.
The File name for all Intro Text Files is just plain "INTRO" and extensions
of course. But they must be inside the correct directory of the area the
intro is to be viewed.
Example : An intro for Message Areas would be "MSGAREA:Intro.T280"
Example : An intro for a Message Area called "General Messages" would
be "MSGAREA:General Messages/Intro.T280"
Example : An intro for File Areas would be "FILEAREA:Intro.T280"
Example : An intro for a File Library called "Amiga Files" Would be :
"FILEAREA:Amiga Files/Intro.T280"
Example : An intro for a File Area called "Utilities" which is inside
the "Amiga Files" Library would be-
"FILEAREA:Amiga Files/Utilities/Intro.T280"
Example : An intro for an Online Program Directory called "Brain
Games" would be "OLP:Brain Games/Intro.T280"
Example : An intro for the partyline would be called "PLINE:Intro.T280".
4.3 Special Program Text Files
Special program text files or otherwise known as SPT files are special
text files that are displayed during various ares of the BBS. These text
files are mainly used to launch special Arexx programs, however; they can
very well just display any text or ansii. The file format for SPT files are
"TEXT:{name}.SPT". For example, the logoff special program text file would
be "TEXT:LOGOFF.SPT". There is no need to put the parser intiater at the
beginning of the file since these files are mainly used for Arexx program
launching, Trinity will default parser enabled. Please see Parser Commands
and also Online Programs for information on running online Arexx programs
within text files. Note: SPT files do not need any other special extensions
to their filenames.
The following SPT files are currently supported:
A) File: "TEXT:MAINTENANCE.SPT"
This SPT is checked immediately after auto maintenance has finished. It
could be used to run nightly OLP maintenance programs.
B) File: "TEXT:LOGOFF.SPT"
This SPT is checked after a user has logged off, but before dropping
carrier. A possible use for this file is to update tables of what the
user did this call to be used in a TOP 10 list or some sort.
C) File: "TEXT:REPLY.SPT"
This SPT is checked after a user has replied to a message in the message
areas.
D) File: "TEXT:POST.SPT"
This SPT is checked after a user posts a message in the message areas.
E) File: "TEXT:NEWUSER.SPT"
This SPT is checked after a user has completed the initial new user login.
A possible use for this file would be to run an OLP that would automaticly
create and send an email to the user welcoming them online.
F) File: "TEXT:Upload.SPT"
This SPT is checked after a user has successfully completed an upload.
G) File: "TEXT:Download.SPT"
This SPT is checked after a user has successfully completed a download.
More SPT files will be added in future versions of Trinity BBS.
4.4 Bulletin Text Files
All Bulletin Files are located in "BULLETINS:". Bulletins do not use
filename extentions. See Bulletins Section for more information.
PART 5 LOADING AND RUNNING TRINITY BBS
This section will describe how to load and run Trinity Control and A
Trinity BBS Node. You should have the system completely configured by now,
otherwise unpredictable errors may occur.
Most of the time you will have Trinity loaded within your "BOOTBBS"
script. However you may run the BBS from CLI as long as all the assignments
and other requirements in your "BOOTBBS" script have been made. Trinity BBS
can not be run from Workbench without special software (XICON, etc.).
5.1 Loading Trinity Control
Trinity Control must be loaded before any nodes are run. Control
will completely handle all IPC between nodes as well any type of request.
Trinity Control is also your only means of examining the status of nodes and
the users who may be on them if the node is iconified. See Section 6.0:
Trinity Control Options for more information.
The command line for Trinity Control is quite simple and it should
be loaded in your "BOOTBBS" script. To run Trinity Control either add to
your "BOOTBBS" script or type at the cli prompt "RUN TRINITYCONTROL". You
may also pass the following arguments:
'-s' - Tell Control not to open its own screen but to open on workbench
by default. Note, the view window will not open on workbench on
the node status window will be displayed.
'-i' - Tell Control to open in an iconified state by default. If you do
not give the '-s' also, when you uniconify, it will open it's own
screen.
5.2 Loading A Trinity BBS Node
After Trinity Control is up and running you can start a node by using
the load menu item of the Control Screen (or Workbench Screen, if Control
is not opened on it's own screen). See section x.x: Trinity Control for
detailed information. Usually you would have all your nodes automaticly
run in your "BOOTBBS" script, however you may load a node via CLI as well.
To load a node from cli or in your "BOOTBBS" script you would type
"RUN TRINITYBBS {node#} -i". The {node#} is the node number you wish to
load. The '-i' arguement tells the node to open iconified. Each node
will accept several command line arguements and they are:
'-i' - Open in iconified mode (Trinity Control will show the
status)
Otherwise, the node will open its own screen (uniconifed).
'-s{device}' - The serial device to use (overrides the field in the node
config). The '-u', '-b' flags must also be used otherwise
it will use the defaults for the device.
'-u{unit#}' - The serial device's unit to use.
'-b{baud}' - Open the serial device with a port speed of given baud rate.
Note, If '-s', '-u', '-b' is used the node will consider that the node is not
suppose to answer the incoming call and that it has already been answered by
some other program (which would call the node to load with those settings).
The node will load and automaticly go into answer/connect mode and show the
login text file (as if it answered and connected a call). After the user logs
off, the node will automaticly shut itself down. This is usefull for use of
such programs as Getty for UUCP, internet, and other usefull reasons. Which
would allow programs like Getty to answer the incoming calls and transfer the
connection to a node when and if needed. And since the node will automaticly
closed itself down, the memory of the node will be free for other uses.
When a Node is loaded it will load the Main Configuration into memory
and its very own Node Configuration. You should of created both of these
using the TrinityUtility program. It will also load in the Menu Command
Configurations. (See Editing and Adding Commands).
PART 6 TRINITY CONTROL OPTIONS
Trinity Control is the heart of the Trinity BBS package. It will
control all nodes and as well as keep a constant status of users on each
node. When loaded it will open a status window show status information
of each node. The node that is highlighted is the current active node.
Trinity Control can send commands to the active node only. If you opened
control in full screen mode (Control opend its own screen) or if you
toggle the workbench/screen menu item, You will also see a view window.
This window will be used to display all OLMS, PARTYLINE, and IPC messages
from nodes. If you have Control opened in interlaced mode this view
window will be larger. The benefits of the view window can not be used
unless Control is in full screen mode and not on workbench.
6.1 Trinity Control Menu Items
Control has the following available menu items:
MAIN OPTIONS: These options are for Trinity Control self usage.
Window/Screen - This will toggle between workbench-window to full screen
mode.
Iconify - This will iconify Control to a small rectangle window on
your workbench screen. You will be unable to see any
status from control while it is iconified. Double click
on the icon or toggle this option again to reopen.
Interlaced - This will toggle the Control screen to interlaced or non
interlaced mode. If a check is by the option the screen
should be in interlaced mode. Note, Contol must be in
full screen mode before this option will have any effect.
Quit - This will first attempt to shutdown all nodes and then
will shut down control. If a node refuses to shut down
Control never will also refuse. It is best to shutdown
all nodes manually before attempting to shutdown Control.
VIEW WINDOW: These options are for identifying what the view window
will display. If a check mark is by an option it will
be displayed in the view window.
Partyline - This will allow the view window to display all PARTYLINE
messages.
OLMs - This will allow all OLMS passed between nodes to be
captured to the view window. This is usefull to see
user's OLMS as the are sent.
Node Msgs - This will allow all IPC message information to be
displayed on the view window. This is usefull for
detecting any problems with nodes.
SpeechON - This is a nice feature that if selected will speak all
view window information to the SPEAK: device. This is
a great way to hear Partyline messages. However, this
WILL lock Control while it is speaking causing delays
in OLMS and partyline messages between nodes.
NODE OPTIONS: These options are used to control nodes. They will only
control the current active(highlighted) node only.
Load - This will load the active node. The node must not
already be loaded. The node will be loaded in an
iconified state.
Open - This will un-iconify(open the node's screen) the node.
Close - This will iconify(close the node's screen) the node.
ResetModem - This will signal the node to reset it's modem.
ShutDown - This will attempt to shut the node down (freeing all
used memory). Note if you shut down a node while a
file transfer is in progress, it will abort the
transfer first.
USER OPTIONS These options will control various aspects of the user
who is currently on the active(highlighted) node only.
Incr Time+10 - This will add 10 minutes of extra time to the user.
You should not do this if maintenance is about to
occur.
Decr Time-10 - This will subtract 10 minutes of available time to the
user.
Incr Acl+1 - This will increase the users access level by 1.
Decr Acl-1 - This will decrease the users access level by 1.
Force Logoff - This will completely force the user off the node.
6.2 Trinity Control Status Window
The status window of Trinity Control will show information of all nodes.
It is able to show up to 5 nodes on the same window at one time. To scroll
up the list of other nodes you can use the arrow keys (make sure you have made
the status window active by clicking on its window, otherwise you may see
the screen flash if in full screen mode or nothing in workbench mode). The
information shown is the Handle, Total Posts, Email, Dls, Uls this call,
time remaining, and the current status of the user on the each node as well
as the last message received or given to the current active node.
To activate a node allowing for menu items to use the node as well as
messages from that node, you must highlight the node. To do this either use
the arrow keys to move the highlighted bar until the node desired is
highlighted or click the mouse on the line of the node's status.
PART X TRINITY BBS NODE OPTIONS
The program "TRINITYBBS" located in the "TRINITY:" directory is main
program fo each node. Each node requires that Trinity Control be
available. The first request each node makes to Trinity Control is for the
address of the nodebuf structure. If it can obtain (if Trinity Contro is
not responding) this address it will abort with an error. A node can be
openned either iconfied (all status is shown by Trinity Control) or can
open on it's own screen allowing detailed status of the user online as well
as be able watch the users i/o as they do. In this section I will describe
all the options available on a node of Trinity BBS.
x.1 Awaiting For A Call
The BBS will constantly check the serial port for a ring. If it
detects a ring the BBS will send the "ATA" command to the modem, which
means the modem will send an answer tone. At this time the BBS will wait
for a carrier. If a carrier is present the BBS will adjust its baud rate
to the incomming baud rate and log the user online, otherwise after a few
seconds the BBS will reset and wait for calls once again. While the BBS is
in this waiting state it will display daily statics of your BBS as well as
the last 5 callers since last update of the node. A local call can be made
by pressing the space bar (mark sure your click on the middle of screen first
to make the main window active). You may also do a quick SYSOP login by
pressing the 'L' key.
X.2 Trinity BBS Node Menu Items
Each Trinity BBS node uses the following Menu Items :
SYSTEM OPTIONS :
Logon : Selecting this or pressing the space bar will initiate
a local logon.
Quick Logon : Selecting this or pressing 'L' will initiate a SYSOP
local logon. Account #1 will be used and will bypass
initial logon procedures.
Send ATA : Selecting this will force the BBS to send an "ATA"
without waiting first for a ring detection.
Reset : Selecting this will RESET the modem used if needed.
Do Maintenance : Selecting this will force the BBS to do auto-
maintenance even if it is not time to do maintenance.
Shut Down : Selecting this will cause the current Node to close
down, freeing all memory used.
ENVIRONMENT :
Status Window : Selecting this will open or close the status window.
SySop Options : Selecting this will force the BBS to go to SYSOP
options. If a user is online it will notify the user
that the SYSOP is doing maintance. All output will
go to the local screen only until SYSOP options has
been exited.
SySop In : Selecting this will toggle the SYSOP In Default a
check mark = YES. (See Main Configuration)
UD Closed : Selecting this will toggle the UD Closed Default.
MSG Closed : Selecting this will toggle the MSG Closed Default.
OLP Closed : Selecting this will toggle the OLP Closed Default.
Speach ON : Selecting this will toggle Speaking Login Annoucements.
USER OPTIONS :
Chat Mode On/Off : Selecting this will enter chat mode. You can chat
with the current online user. Selecting it again
or ESC will exit.
Force Logff : Selecting this will force the current user off the
system.
Incr Time +10 : Selecting this will add 10 minutes to the current
user's time limit. Note this will not have an effect
if midnight maintenance is near.
Decr Time -10 : Selecting this will subtract 10 minutes from the
current user's time limit.
Incr Access +1 : Selecting this will increace the current users
access level by 1.
Decr Access -1 : Selecting this will decrease the current user's
access level by 1.
x.3 Status Window
The status window displays information about the current user or the
last user online. It also will display satus information on what the BBS
is currently doing, example Awaiting For A Call, Maintenance, ect...
The status window may be open or closed via its menu item.
X.4 Logging On The BBS
When a caller logs in or a local call occurs, the BBS will go to the
logon section. The user will be asked if he/she would like to log on using
ANSI. Afterwards, the LOGIN test file will be displayed. Next, the user
will be instructed to enter his/her account number or username and
password or NEW for new user. The user will get five tries to correctly
login, otherwise he/she will be forced off the system.
x.5 New User Log On
When a new user calls (which even you will have to during your first
call) the BBS will initiate the new user application process. The text
file NEWUSER will be displayed at this time and several questions will be
asked. He/She should answer these questions truthfully before you should
give them access. The new user access level is always 0.
PART X MAIN MENU
This section will describe all options and features available at the
Main Menu. Some options require a higher access level than others. I will
use the default commands but you can edit or add commands (See Editing And
Adding Commands).
6.1 Main Menu Commands
(G) GoodBye Or Logoff
When the user presses "G", he/she will be sent to the logoff section.
He/she will be asked if he/she is sure that he/she wants to logoff and
whether or not he/she would like to leave the SYSOP feedback before
logging off. The LOGOFF text file will be displayed and all the user's
new stats will be saved.
(M) Enter The Message Areas
This command will take the user to the Message Area section. Trinity
uses a very sophisticated message handling routine. In this section
users can post and read public messages.
(F) Enter The File Transfer Areas
This command will take the user to the File Transfers Section.
(E) Enter The Electronic Mail Section
This command will take the user to the E-Mail (Private Messages)
Section.
(B) Enter The Bulletins Or Text Files Section
This command will take the user to the Bulletins Section where he/she
may read text files.
(O) Enter The Online Programs Section
This command will take the user to the Online Programs Section.
He/she can play games and other online programs.
(U) Userlog List
This command will display a list of all the users on the BBS. It will
display their name, location (city & State), computer, and the last time
they called.
(C) Page The SYSOP For Chat
This command will first ask the user why he/she is wanting to chat
with the sysop? Next it will, check the status of the SYSOP In default.
If it is set to false (no) it will tell the user that the SYSOP is not
available and ask if he/she would like to leave the SYSOP feedback. If
it is true (yes) it will play a digitized IFF file (filename TRINITY:
Pager.SND) and open a window displaying the reason for chat. The SYSOP
may break into chat mode by using the menu item under User Options.
(L) Leave The Sysop Feedback
This command will allow the user to leave the SYSOP a feedback message.
Feedback is always mailed to the SYSOP username that you entered in the
Main Configuration.
(T) Time Information
This command will display to the user information about his time limit.
It will display his access level, the time he/she logged on, the time
he/she logged off, and the amount time remaining.
(P) Password Change
This command will allow the user to change his user account password.
($) Edit Profile
This command will allow the user to edit his/her user profile which
includes his name, address, phone number, ect. The user may also, if
you give them the priviledge, create or upload their signature file
to be used in message and email posting.
(#) Edit Terminal Paramaters
This command will allow the user to edit his/her terminal paramaters
that are being used on the BBS which include terminal type, columns,
rows, hotkeys, ect.
(*) Sysop Options
This command will take the user to the SYSOP OPTIONS.
(N) Change New Item Date
This command allows the user to change his/her last new item date.
This date is used when reading new messages, listing new files, ect.
The user is also asked if he/she would like to edit this date during
these operations.
(J) Join The PartyLine
This will take the user to the Partyline Global node conferencing section.
PART 7 MESSAGE AREAS
Trinity uses very sophisticated routines in handling messages. Messages
are saved in a sequential order - The original post which starts out the topic
and then it's replies. These are stored in one file which saves time and
directory space. This also makes it easier for the reader to understand what
is being read without getting confused on what someone is replying to.
7.1 Message Menu Commands
(Q) Quit Back To The Main Menu
This command will take the user back to the main menu.
(G) GoodBye Loggoff
See main menu commands.
(C) Chat With The SYSOP
See main menu commands.
(R) Read Messages
This command will allow the user to read messages in the current message
area. The user will be asked if he/she would like to read (F)orward,
(N)ew, Or (G)lobal. Global will read messages in all joined areas and
also with a choice of forward or new. See reading messages.
(P) Post A Message In The Current Area
This command will allow the user to post a new message topic in the
current area. This message may then be able to receive replys. See
posting messages.
(S) Scan Messages
This command will allow the user to scan messages in the current
message area. The user will be asked if he/she would like to scan
messages (F)orward, (N)ew, or (G)lobal. Global will scan messages in all
joined areas and also with a choice of forward or new. The user will be
showed the topic of the message group and will be asked if he/she would
like to read this message group. See reading messages.
(J) Join/UnJoin current area
This command will allow the user to join or unjoin (if joined) the
current message area. If a user does not have an interest in a certain
message area, he/she can unjoin it and it will not be used during a global
read or scan.
(L) List Message Group Topics
This command will display a list of all the message group topics in
the current area. It will display the message group #, it's total replys,
the original post's author, the topic of the message group, and the date it
was last replied.
(A) Change Message Areas
This command will allow the user to change to a different message area.
All message areas that the user has access to enter will be displayed. An
astrix will be displayed with all joined areas.
(E) Add/Edit Message Areas
This command will allow the user (usually SYSOP) to add a new message
area or edit the current message area. See adding and editing message
areas.
7.2 Reading Messages
When reading messages the user has a choice of forward read, new read,
or global read. Forward reading will view all messages starting from
message group 1 to the last message group in the area. Reading new will
view only the message groups that have new replies since the last time the
user called. The user will be asked if he/she would like to change their
read new date before proceeding with the new read. Global reading will
read messages either forward or new in every joined message area starting
from the first available message area to the last.
While the user is reading messages he/she will come across several
reading commands. And they area :
(R) Reply
This allows the user to add a new reply to the current message group
he is reading. Note : There are a limit to 100 replys per message group
to save time when reading new messages. The user will be asked who this
reply is to be address to. If the user presses return at this prompt, the
name of the last read reply will be used. Next, the user will be brought
to the Trinity text editor. See Trinity Text Editor.
(N) Next
This will continue to the next reply in the current message group or to
the next message group if all the replys have been read. If the user
has reached the end of the message groups in the current area and is
reading global he/she will be asked if he/she would like to Post a new
message topic in the current area or Quit Reading Here.
(B) Beginning
This will transfer the user to the beginning of the current message group
or reply #0 (original post) and then will continue reading from there on
to the end of the message group.
(J) Jump
This will allow the user to move (jump) to a certain reply number of the
current message group. This is usefull if the user gets confused or
lost in the conversation and would like to go back a few replys to get
caught up on what is being said.
(S) Skip
This will allow the user to skip the current message group and go to
the next. This is usefull if the user is not interested in the
conversation that is going on with the current message group topic.
(Q) Quit
This will allow the user to quit reading messages. If the user is
reading messages via global, then the BBS will continue onto the next
message area.
7.3 Posting Messages
When posting messages, the user is actually starting a new message topic
in the current message area. Other users may reply to this message and
it's replys. This is how conversations are started. The user will be
asked the name of the user this message is to be posted to or ALL. Next,
the user will be asked the Title or Topic of the message. If the user has
access, he/she will be asked whether to post anonymously or with an alias.
The user will the be brought to the text editor. See Trinity Text Editor.
7.4 Trinity Text Editor
Trinity BBS uses a built in text editor that has some pretty useful
features :
* Inserting Lines
* Deleting Lines
* Editing Lines
* Read output as will be viewed
* List output as entered with line numbers
* Allows Parser Commands (See Parser Commands)
* Word Wrap
* Uploading Pre-Written Message via ASCII
When using the editor for posting and replying messages the user will be
rewarded with a certain amount of download and olp credits per line of
text based on the information in the Main Configuration.
7.5 Adding Message Areas
Trinity BBS supports up to 99 different message areas. Each message area
can have an unlimited amount of messages. When adding a new message area
the user (usually SYSOP or SUBOP) must answer several questions :
Area Title : 'Enter the name of this new message area here.
Access Level : 'Enter an access level required before even seeing
this area on the list or 0 for everyone.
Password : 'Enter a password if you wish a password to be
required before entering this area. Press
RETURN for none.
Youngest Age To Enter : 'Enter an age minimum to enter this area or 0 for
everyone.
Oldest Age To Enter : 'Enter an age maximum to enter this area or 0 for
everyone.
Auto-Deletion Months : 'Enter the number of months before a message group
is auto-deleted by maintenance. The date it uses
is the last date the group was replied to. Enter
0 for never allowing messages to be auto-deleted.
PART 8 E-MAIL AREA
E-Mail (Electronic Mail) is a private message area where users can
send and receive private messages to and from other users. Users will be
notified of email waiting during the initial login.
8.1 E-Mail Menu Commands
(S) Send Someone E-Mail
This command will allow the user to send other users E-Mail.
(R) Read Your E-Mail
This command will check to see if the current user has E-mail and
allow him/her to view email waiting. See Reading E-Mail.
(A) Read All E-Mail (usually SYSOP)
This command will allow the user to read all E-Mail on the system.
The user will be ask to read new mail only which will only display email
that has been mailed since his/her last new item date. This date can be
changed since it will ask the user if he/she would like to change it.
Version 2.0 allows the user to specify the users handle they would like
to search on. See Reading E-Mail
(Q) Quit To The Main Menu
This command will take the user back to the Main Menu.
(G) GoodBye or Logoff
See Main Menu Commands
(C) Page SYSOP For Chat
See Main Menu Commands
(U) View UserLog
This command will allow the user to view the userlog in case he/she
forgets the exact username of the user he/she would like to send E-Mail.
8.2 Reading E-Mail
Reading E-Mail on Trinity BBS is a quick and easy process. A users
E-Mail will be displayed and deleted after he/she reads it unless he/she
decides to keep it for some reason. There are a few commands the user has
while reading messages and they are :
(A) Again
This command will allow the user to view the current E-Mail over
again.
(K) Keep
This command will keep the current E-Mail message and will not delete
it. This is useful if the user does not have time to reply at the present
but may keep it and reply to it on his/her next call.
(R) Reply
This command will allow the user to reply to the current E-Mail
message. The new E-Mail message will be sent to the user the current
E-Mail message is from.
(V)iew/Edit User
This command will allow the user (usually SYSOP) to view or edit the
sendee's account.
(Q) Quit
This command will allow the user to stop reading his/her E-Mail and
can continue reading them later.
Part 9 FILE TRANSFER AREA
Trinity BBS uses very sophisticated routines for handling file
transfers. The BBS uses external protocols including Xmodem, Xmode CRC,
Ymodem Batch, and Zmodem. Other external protocols will be added to new
versions of the BBS as they come available. Trinity can handle 99 file
libraries and each of these libraries can have 99 different file areas. As
soon as a user enters the file transfers section he/she will be asked to
choose a file library. At this prompt a SYSOP command is available to Add
or Edit File Libraries. See Adding File Libraries.
9.1 File Transfer Menu Commands
(A) Change To A Different File Area
This command will allow the user to change to a new accessable file area
in the current file library. To change to a new file library the user
must exit the file transfers section and re-enter.
(S) Scan All File Areas
This command will allow the user to Scan all File Areas in the current
File Library. The user has a choice to only display new files in the
areas. See Viewing File Lists
(L) List Files In Current File Area
This command will allow the user to List files in the current file area.
The user has a choice to only display new files. See Viewing File Lists.
(B) Browes Files
This command will allow the user to get a detailed information list off
all files in the current area. The user has a choice of browesing new
files only. See File Information
(R) Read Info On A File
This command will allow the user to get detailed information on a file.
The user will be asked the filename or the file # of the file to get
information on. See File Information
(P) Protocol Change
This command will allow the user to change the current protocol being
used. The default is Zmodem.
(D) Download File(s)
This command will allow the user to download (Receive) a file or files
in a batch transfer. See Downloading Files.
(U) Upload File(s)
This command will allow the user to upload (Send) a file or files in a
batch transfer. See Uploading Files.
(Y) View Your File Status
This command will display to the user, his/her current U/D status on
the system. It will display the total of files and Kbytes he/she has
uploaded and downloaded, remaining credits, remaining time, ect.
(Q) Quit To Main Menu
This command will return the user back to the Main Menu.
(G) Goodbye or Logoff
See Main Menu.
(C) Page SYSOP For Chat
See Main Menu.
(E) Edit/Add File Areas
This command will allow the user (usually SYSOP) to be able to add a new
file area to the current file library or edit the current area. See
Adding File Areas.
(O) Adopt Files
This command will allow the user (usually SYSOP) to odopt (add) files to
the current file area's file list. The file must be already in the
directory of the file area, eg - FileArea:Amiga Files/Utilities/Files
(/) Change Libraries
This command will allow the user to change to a different file library.
9.2 View File Lists
The way the list of files in a current area are display as :
+1 ToolLib.lzh 71k Library For Programs, Useful Routines 10-26-1991
ab c d e f
a : This is the type of file.
"+" = SYSOP Favorite : The SYSOP usually likes this file and gives
high respect for it.
"*" = Free Download : The SYSOP has made this file a free download
meaning it will not take any credits to
download.
A Blank Space means it is a regular file.
b : This is the file number of the file.
c : This is the file name of the file. New Files will be displayed in bold
and unvalidated files will be displayed in italics.
d : This is the actual size of the file in Kbytes. It is also the amount
of UD Credits required to be able to download this file unless of course
it is a free download.
e : This is the short description of the file. A Longer description may be
viewed by reading information on the file.
f : This is the date the file was uploaded, edited, or odopted.
Once the the user has reached the end of the file list or the screen
has been full with files he/she will be given a set of commands :
(N) NonStop
This command will allow the user to view the list without any command
interruptions even if the screen is full until the end of the list.
(Q) Quit
This command will take the user back to the File Menu.
(M) Mark
This command will allow the user to mark a file for download. The user
will be asked either the file number or filename of the file he/she
wishes to mark. Note : Xmodem users can only mark one file at a time.
(C) Continue
This command will continue with the list of files.
(D) Download
This command will allow the user to download his/her marked files as well
as mark more files. Note : Xmodem users can only download 1 file at a
time. See Downloading Files.
9.3 File Information
A file's information is displayed during browesing of files or when
the read information on a file command is in use. Several pieces of
information is displayed about the file to the user and these include :
File Number : 1 Validated
a b
Downloaded : 36 times
c
File Name : ToolLib.lzh
d
Length : 72850 Bytes
e
Extimated Time : 1 Min(s) at 9600 Baud
f
Credits Needed : 71
g
Uploaders Name : ACTION
h
Date Uploaded : 10-26-1991
i
Description : Library For Programmers, Useful Routines
j
This is a really neat library. It supports several usefull routines.
All Programmers should check it out.
k
a : This is the file number of the file
b : This is the status of the file. It will be either Validated,
Unvalidated, or a SYSOP Favorite.
NOTE : Users can not downloaded unvalidated files.
c : This is the total number of times the file was downloaded. This is
useful to a user so he can know if the file is a popular download or not.
d : This is the file name of the file.
e : This is the actually length of the file in bytes.
f : This is the extimated time it will take for a user at his/her baud rate
to download.
g : This is the total number of credits that are required to download this
file. It may also display * Free Download *, which means that the SYSOP
has decided to make this file free to all users to download.
h : This is the username of the user who orginally uploaded this file.
i : This is the date the file was uploaded, edited, or odopted.
j : This is the short description of the file.
k : This is the long description of the file which also may contain
comments from other users.
The user has a choice of several commands at this point :
(V) Validate
This command will allow the user (usually SYSOP) to validate the file.
This is will toggle from unvalidated to validated, from validated to SYSOP
favorite, and from SYSOP favorite back to unvalidated.
(E) Edit
This command will allow the user to edit the description of the file
and also be able to make it a free download.
(*) Move
This command will allow the user (usually SYSOP) to move the file to a
different file area.
(K) Kill
This command will allow the user (usually SYSOP) to delete the file
from the file list.
(Q) Quit
This command will take the user back to the File Menu.
(M) Mark
This command will allow the user to mark the file for download. Note
Xmodem users can only mark one file at a time.
(D) Download
This command will allow the user to download the file. See Downloading
Files.
(N) Next
This command will continue onto the next file during a browes or back
to the file menu during a read file info command.
(C) Comment
This command will allow the user to add a comment to the file. The user
may write how much he/she liked or disliked the file.
9.4 Downloading Files
Trinity BBS allows batch file transfers as well as single file
transfers. The user will be asked the files to download. Hitting return
on a blank filename will bring a list of all the files that are marked for
downloading. If these files exceed the users time limit or the amount of
download credits he/she has, he/she will be informed and the BBS will not
allow the download unless some files are removed and they fit the time
limit and credits. At this point the user will be given a set of commands:
(A) Abort
This command will abort the download and bring the user back to the
file menu.
(R) Remove
This command will allow the user to remove some files from the list to
lower the amount of time and credits needed.
(P) Protocol
This command will allow the user to change his/her protocol before
starting the download.
(S) Start
This command will actually instate the download process. An external
protocol window will come up and the file transfer will begin.
9.5 Uploading Files
Trinity BBS uses batch (multible) file transfers as well as single
file transfers. During an xmodem (single) file transfer the user will be
asked the file name of the file to upload. During batch transfers (Zmodem,
Ymodem, ect.) the user will not be asked for a file name since these
protocols send the filename automaticly. The user will be given the amount
of free disk space before uploading and will have a choice of commands :
(A) Abort
This command will abort the upload and take the user back to the file
menu.
(P) Protocol
This command will allow the user to change his/her protocol before
continueing with the upload.
(S) Start
This command will start the upload process. An external file transfer
window will open and the file transfer will begin.
Once the file transfer has finished the user will be asked to describe
the file(s) he/she uploaded.
9.6 Adding File Libraries
Trinity BBS supports up to 99 file libraries. This libraries will
hold as many as 99 different file areas. Some examples of file libraries
are : Amiga Files, IBM Files, Machintosh Files, ect. The user (usually
SYSOP) will be asked several questions when adding a new library :
Library Name : 'This will be the name of the new library.
Access Level : 'This is the access level required before
being able to see this library.
Password : 'Enter a password if you would like a
password required to enter or press return
for none.
Youngest Age To Enter : 'Enter an age minimum for someone to enter
this file library or 0 for all.
Oldest Age To Enter : 'Enter an age maximum for someone to enter
this file library or 0 for all.
Next, the user will be asked to if he/she would like to add this new
file library. If Yes, the file library will be added to the list and is
ready to have it's file areas added.
9.7 Adding File Areas
Trinty BBS supports up to 99 file libraries and each of these
libraries can have as many as 99 file areas. Some examples of some file
areas in a file library called Amiga Files area : Games, Utilities, Misc
Programs, Communications, ect. The user (usually SYSOP) will be asked
several questions when adding a new file area :
File Area Name : 'Enter the name of the new file area here.
Access Level : 'This is the access level required for being
able to see this file area.
Password : 'Enter a password if you would like a
password asked before entering this area.
Youngest Age To Enter : 'Enter an age minimum before for someone to
enter this new file area or 0 for all.
Path Location Of Files : 'Enter the location that you wish the files
of this area are to be stored. Note a default
is given and pressing return will use this
default.
Deletion Months : 'Enter the amount of months before
auto-maintence will auto-delete a file or
enter 0 for never.
Auto-Validate Files : 'Enter YES if you wish all files in this file
area to automaticly be validated at time of
upload.
Space Minimum : 'Enter the minimum amount of disk space in
kbytes allowed before an upload, example
500.
Allow Uploading : 'Enter YES if you wish uploads to be allow in
this area.
Next, the user will be asked if he/she would like to add this new
area. If yes, the new file area will be added to the file library's list
of areas and it will be ready to receive new files.
Part 10 SYSOP OPTIONS
Trinity BBS offers a special area for users with SYSOP access or in
otherwords with SYSOP priviledges set. Some very useful commands are
included in the SYSOP options. Expect more commands in future versions or
mods.
10.1 SYSOP Menu Commands
(U) User Log List
This command will display a list of users on the system.
(E) Edit/View an Account
This command will allow the user to view and/or edit a user on the BBS.
It will ask for an account number or a username. See Editing Users
(A) Edit Users With A Certain Access Level
This command will allow the editing of only users with a certain
access level. This comes in handy when you would like to edit only new
users. It will ask you an access level to search and all users with this
access level will be available to edit. See Editing Users
(G) Add/Edit an Access Group
This command allows the adding or editing of access groups. These
groups define an access level. See Access Groups
(N) News Writer
This command will bring you to the News Writing Area. This area is
used for writting news files that are displayed at login.
(D) Dos Shell
This command will open up a new cli so remote users can issue cli
commands... Use caution with this command.
(F) File Editor
This command will allow the user to edit any text file. It is
recommended to use an external editor but this is useful for quick
editing.
(Q) Quit Back To Main Menu
This command will bring the user back to the Main Menu.
(V) View System Logs
This command will allow the viewing of system logs including Caller
Log, Download Log, Upload Log, and Maintenance Log. You may reset
the logs after viewing them.
(*) NODE UTILITIES
This command gives the user a list of special commands that is used
to control inter-node communications and they are:
(F) Force Logoff
This will attempt to force the user currently on the given
node off the system.
(S) Shut Down
This will attempt to shut down the given node, freeing up all
memory used.
(G) Give More Time
This will attempt to give the user currently on the given node
additional specified minutes of time. Note: If auto maintenance
is plan to occur the actual time given will be truncated as needed.
The user on the node will be notified of the addtional time.
(T) Take Away Time
This will attempt to take away specified time from the user currently
on the given node. The user on the node will not be notified of the
time taken away, unless of course they check their time left.
(B) Broadcast Message
This will allow the user to send a global online message from
System Administration. This OLM can not be replied to. It will
also override hidden and unavailable flags, so that everyone
online will receive this message.
10.2 Access Groups
Trinity BBS uses access groups or access level descriptions as part of
the access level for a user. Each access level has it's own descriptive
name and set of priviledges and limits. When you change a user's access
level the user receives all the priviledges and limits that is included in
this access level (access group) You should never give a user an access
level that has not been defined which means you must define all access
groups (levels) even an access level of 0 (new users) must be defined. a
filename of ACGROUP.n where n is the access level will be stored in
CONFIGURATION:. The sample setup has 4 different examples of access
groups.
10.3 Priviledges
Inside of an access group or user account is an array of priviledges
which basicly outline the access level. Priviledges are either set to YES or
NO (on/off). When you select edit priviledges while editing users or access
groups you will be given a grid of the priviledge flags. You can move to
the next flag by pressing 'RETURN or 'TAB'. You can move back to the
previous flag by pressing 'DEL' or 'BKSPC'. To toggle a flag press the
'space bar'. After you are finished with editing all flags press the 'ESC'
key to store them. These priviledges will actually define what the user is
allowed to do and they are:
*ABILITY TO LOGIN
If this priviledge is set to NO, the user will not even be able to
logon to your BBS.
*MSG AREAS
If this priviledge is set to NO, the user will not be allowed to enter
the message areas of the BBS.
*FILE AREAS
If this priviledge is set to NO, the user will not be allowed to enter
the file transfer areas of the BBS.
*E-MAIL AREAS
If this priviledge is set to NO, the user will not be allowed to enter
the E-Mail area of the BBS.
*ONLINE PROGRAMS
If this priviledge is set to NO, the user will not be allowed to enter
the online programs section of the BBS.
*BULLETIN AREAS
If this priviledge is set to NO, the user will not be allowed to read
bulletins.
*VIEW USERLOG
If this priviledge is set to NO, the user will not be allowed to view
the list of users.
*PARTYLINE
If this priviledge is set to NO, the user will not be able to enter the
partyline.
*LEAVE FEEDBACK
If this priviledge is set to NO, the user will not be able to leave you
feedback.
*SHOW WHO ONLINE
If this priviledge is set to NO, the user will not be able to see a list
of user who are currently online other nodes.
*SEND OLMS
If this priviledge is set to NO, the user will not be able to send or
reply to Online Messages to/from other users currently online other
nodes.
*RECEIVE OLMS
If this priviledge is set to NO, the user will not be able to receive
Online Messages to/from other users currently online other nodes.
*GLOBAL OLMS
If this priviledge is set to NO, the user will not be able to send
global online messages to all other users currently online other nodes.
*HIDE FROM USERS
If this priviledge is set to NO, the user will not be able to hide
themself from other users currently online other nodes.
*SEE HIDDEN USERS
If this priviledge is set to YES, the user will be able to see who is
on all other nodes whether they are hidden or not.
*EDIT OWN PROFILE
If this priviledge is set to NO, the user will not be able to edit his/her
handle, address, phone number, ect. This is handy because a user may
try to change their age once they notice a limit in one of your message
areas or something of that sort.
*SIGNATURES
If this priviledge is set to NO, the user will not be allowed to edit or
upload their signature file.
*PASER CMDS LEVEL 1
If this priviledge is set to YES, the user will be able to use level 1
parser commands. See Parser Commands
*PASER CMDS LEVEL 2
If this priviledge is set to YES, the user will be able to use level 2
parser commands. See Parser Commands
*PASER CMDS LEVEL 3
If this priviledge is set to YES, the user will be able to use level 3
parser commands. See Parser Commands
*BY-PASS MSG LIMITS
If this priviledge is set to YES, the user will be able to by-pass any
message posting/replying limits that he/she may have.
*BY-PASS E-MAIL LIMITS
If this priviledge is set to YES, the user will be able to by-pass
E-Mail posting limits that he/she may have.
*BY-PASS U/DLD LIMITS
If this priviledge is set to YES, the user will be able to by-pass any
Uploading and Downloading limits including credits.
*BY-PASS TIME LIMIT
If this priviledge is set to YES, the user will be able to by-pass any
time limits that he/she may have. This does not include the forced
allocated time for maintenance. Even a SYSOP can't get around this!
*BY-PASS IDLE LIMIT
If this priviledge is set to YES, the user will not have any idle time
limit; The user can stay idle up to his/her time limit.
*BY-PASS CALL LIMIT
If this priviledge is set to YES, the user will be able to by-pass any
call limits that he/she may have.
*BY-PASS OLP LIMITS
If this priviledge is set to YES, the user will be able to by-pass any
Online Programs credit limits.
*BY-PASS PLINE LIMITS
If this priviledge is set to YES, the user will able to by-pass any
partyline restrictions.
*BY-PASS PASSWORDS
If this priviledge is set to YES, the user will be able to by-pass
any password requirements in message areas and file areas.
*ANONYMOUS POSTS
If this priviledge is set to YES, the user will have the ability to
post messages anonymously.
*ALIAS POSTS
If this priviledge is set to YES, the user will have the ability to
post messages with an alias.
*TRACE ANONYMOUS
If this priviledge is set to YES, the user will have the ability to
see who posted anonymously or used an alias.
*DELETE ANY MESSAGE
If this priviledge is set to YES, the user will have the ability to
delete any message group in any area.
*DELETE OWN MESSAGES
If this priviledge is set to YES, the user will have the ability to
delete any message group he/she originally started.
*DELETE ANY FILE
If this priviledge is set to YES, the user will have the ability to
delete any file in any file area.
*DELETE OWN FILES
If this priviledge is set to YES, the user will have the ability to
delete any file he/she uploaded.
*DELETE ANY E-MAIL
If this priviledge is set to YES, the user will have the ability to
delete any email message.
*AUTO VALIDATE FILES
If this priviledge is set to YES, any file the user uploads will
automaticly be validated.
*ADOPT FILES
If this priviledge is set to YES, the user may adopt files in a file area.
*READ ALL E-MAIL
If this priviledge is set to YES, the user will be able to read any and
all users email.
*EDIT MSG AREAS
If this priviledge is set to YES, the user will be able to edit and add
any message area.
*EDIT FILE AREAS
If this priviledge is set to YES, the suer will be able to edit and add
and file area or library.
*EDIT BULLETINS
If this priviledge is set to YES, the user will be able to add or delete
any bulletin file.
*EDIT OLP AREAS
If this priviledge is set to YES, the user will be able to edit and add
the online program area.
*SYSOP OPTIONS
If this priviledge is set to YES, the user will be able to enter the
SYSOP MENU.
*VIEW USERS
If this priviledge is set to YES, the uiser will have the ability to
view user accounts and information except user passwords unless that
priviledge is set as well. This priviledge does not allow the user to
edit accounts, a seperate priviledge is available for editing.
*VIEW PASSWORDS
If this priviledge is set to YES and the view users priviledge is also
set the user will have the ability to view user accounts and information
including their passwords.
*EDIT USERS
If this priviledge is set to YES, the user will be able to edit user
accounts and information, however this priviledge does not allow the
user to edit their own account or change another users access to a
level higher than their own.
*EDIT SELF
If this priviledge is set to YES, the user will have the ability to
edit their own account and access. This restriction is useful if you
wish to have co-sysop level access but do not want your co-sysops to
be able to change themselfs to full sysop access (unique to Trinity).
*VIEW LOGS
If this privilege is set to YES, the user will have the ability to view
all log files.
*EDIT NEWS FILES
If this priviledge is set to YES, the user will have the ability to
edit news files.
*FILE EDITOR
If this priviledge is set to YES, the user will have the ability to
edit files via the file editor.
*NODE UTILITIES
If this priviledge is set to YES, the user will have the ability to
access the SySop node utility menu.
*VIEW PLINE PRIVS
If this priviledge is set to YES, the user will have the ability to
see all partyline private messages while they are in the partyline.
*JOIN ANY PLINE AREA
If this priviledge is set to YES, the user will have the ability to
join any partyline area, even if the area is private. This will also
display all private areas if they list areas.
*SNOOP USERS
If this priviledge is set to YES, the user will have the ability to
snoop any node (watch everyone a user sees or does on a node). Note
node 0 or any node with a local call can not be snooped.
*DOS SHELL
If this priviledge is set to YES, the user will have the ability to
enter the dos shell.
Note: Several priviledges will need to go hand in hand... For example
if you give someone the edit users priviledge, they must also have the
sysop options and view users priviledges set as well.
10.4 Limits
Inside of an access group or user account is an array of limits.
These limits will define a users total amount of ability. These limits
include :
*CALLS PER DAY
This is the amount of calls the user is allowed per day.
*TIME LIMIT PER CALL
This is the amount of time in minutes the user is allowed per call.
Note : Maintenance may alter this depending on the time of the call.
*TIME LIMIT PER DAY
This is the amount of time in minutes the user is allowed per day.
Note : This should not be smaller than the Time Limit Per Call. This
would not make much sence.
*DOWNLOADS PER CALL
This is the total amount of files the user may download per call.
*UPLOADS PER CALL
This is the total amount of files the user may upload per call.
*CREDIT RATIO
This is the amount of U/D credits the user receives per Kbyte of an
upload. For example, if the the ratio was set to 3 and the user uploaded
a file that was 100 Kbytes long, the user would receive 300 credits for
the upload.
*MSG LIMIT
This is the total amount of messages the user may write per call.
*E-MAIL LIMIT
This is the total amount of E-Mail the user may post per call.
*OLM's PER CALL
This is the total number of online messages the user may send or reply
per call.
*PARTYLINE MSGS PER CALL
This is the total number of partyline messages (lines broadcasted) the
user is allowed per call
10.5 Editing Users
Editing users on Trinity BBS is fairly simple. You may edit almost
everything in a users account. When you are at the view user prompt you will
have the option of several commands and they are :
(A) Access Level
With this command you may change the access level of the user. When you
change the access level, the access group of the new level will be loaded
into the users priviledges, and limits. You may change this priviledges
and limits if you wish.
(1) User Name
You may edit the user's handle with this command.
(2) Real Name
You may edit the user's real name with this command.
(3) Address
You may edit the user's address with this command.
(4) Voice
You may edit the user's voice telephone number with this command.
(5) Data
You may edit the user's data telephone number with this command.
(6) Gender
You may edit the user's gender (sex) with this command.
(7) Birthdate
You may edit the user's birthdate with this command.
(P) Password
You may change the user's password with this command.
(8) Edit Privledges
You may edit a user's priviledges with this command. See Privledges.
(9) Edit Limits
You may edit a user's limits with this command. See Limits.
(T) Edit Terminal Parameters
You may edit a user's terminal parameters (term type, columns, rows, ect.)
with this command.
(D) Download Credits
You may add/subtract a user's download credits with this command.
(O) OLP Credits
You may add/subtract a user's OLP (On-Line Program) credits with this
command.
(V) View/Edit Signature
You may view/edit the users signature file.
(E) Total Calls Today
You may change the total number of calls the user made today (last call
date).
(F) Total Time Today
You may change the total number minutes the user used today (last call
date).
(K) Kill
You may delete a user from the BBS with this command.
(Q) Quit
This will quit out of the view/edit user screen.
(S) Save
This will save all changes to users account. If the user is currently
online it will automaticly update his/her account online and will
receive an online message stating so.
PART 11 BULLETINS AREA
Trinity BBS uses a special area for information text files. This
files can be anything ranging from a list of local BBSs to high scores on
an online game. Filenames for bulletins can be anything and do not need
file extensions like most other text files on Trinity BBS, since you might
want to add a text file that you receive from some other source to include
on your BBS. Trinity BBS can handle up to 99 different bulletins.
11.1 Bulletin Commands
(K) Kill
This command will allow the user (usually SYSOP) to delete any bulletin
that is on the list.
(A) Add
This command will allow the user (usually SYSOP) to add a new bulletin
to the list. It will ask for a filename and then a description for the
file. The description will be displayed in the list. If the filename
that was entered is not found, the BBS will allow the user to edit/create
the file using the Trinity Text Editor at this point.
(Q) Quit
This command will quit the bulletins area and bring the user back to the
Main Menu.
Entering a number of one of the bulletins listed would display that bulletin
to the user.
PART XX THE PARTYLINE
One of the best features of Trinity BBS is it's multi-node conference
system that I call The Partyline. In the partyline users can participate in
real time multi-user chat. The best features of the partyline are that
every user can define his/her colors and hundreds of available actions. In
fact the SySop can create even more customizable actions.
XX.1 Joining The Partyline
To get to the partyline the user would type 'J' (or the partyline command
if redefined by the SySop) at the main menu. The user will be brought into
the Lobby (actually name is your BBS name and LOBBY). The lobby is the
first area(room) every user will enter. From here users can either stay in
the lobby or create their own public or even private areas.
XX.2 Broadcasting Messages
To broadcast a partyline message, the user simply types what they would
like to say, up to 300 characters and press return. The message will be
broadcasted to all users in the same area. For example if a user named
Sunshine typed 'hello everyone!', all users in the same area will see
Sunshine: Hello Everyone!.
XX.3 Private Messages
Users may also send private partyline broadcasts to other users. These
messages will only show on the receivers node and any users with the view
partyline privs priviledge set. To send private messages, the user would
type /p, which will send the user to the partyline command menu and then to
the private message send routine which will request a handle to send the
private message to. This handle may be truncated as long as no other user is
online who also has a similar handler. For example entering a handle of 'SUN'
would send the private message to 'SUNSHINE'. Next, the BBS will request the
body of the private message to be typed and then it will send the message to
the desinated user. There is also a faster method of sending private messages
that will take away the need to go to the partyline command menu; typing
*{handle} {message body} will also send a private message to the user with the
given handle.
XX.4 Partyline Actions
One of the neat features of the partyline is the ability to issue action
broadcasts. These actions are short verbal sayings that users to do or say
to other users. For example: if a user named 'FIRESTAR' issued the action
'NICEKISS SUNSHINE', Sunshine would see a broadcast message stating "FIRESTAR
kisses you nicely!" All other users would get a broadcast message stating
"FIRESTAR kisses SUNSHINE NICELY!" Firestar would also get a broadcast stating
"You kiss SUNSHINE nicely!". To send actions the user would type as if
they were broadcasting a normal message, '-{action} {towho}'. Notice the dash
before the action name. This dash is required. The receiver is optional on
most actions. Private actions can only be sent by using two dashes instead
of just the one, for example: '--NICEKISS SUNSHINE'. Private actions will
only be seen by the receiver, sender, and any users with view partyline privs
priviledge set. The Trinity BBS v2.0 archive includes approximately 300
different actions and more can be created by the SySop. Read any action file
in the "PLINE:actions" directory for an example.
XX.5 Joining and Creating Public/Private Partyline Areas
When a user first enters the partyline, they are placed in the lobby
area. Users can create their own areas which can be private areas, where
other users without special priviledges can not join unless invited. In
each area only users in the same area will be able to communicate with
each other. However, private messages and private actions may span into
other areas if needed. To join or create a new area the user would press
'/j' which will ask for the area name or number to join or if they would like
to create another room. If they create another room and make it private they
will need to use the '/i' command to invite other users into the area. When
all users leave any area (other than the lobby) the area will no longer be
listed.
XX.6 The Partyline Command Menu
To get to the partyline command menu, the user would type a '/' which
will bing up the command prompt. Here there user can issue commands like
the commands stated in the previous sections. The following are valid
partyline command options as of V2.0 of the BBS:
(?) Command List
This will display a list of all valid commands to the user.
(A) Action List
This will display the file text file "ActionList." See section xxx
text files. This file must be created so users may know what all
the actions are. You may want to include instructions on how to issue
actions in this file as well.
(C) Change Your Configuration
This will allow the user to change his/her partyline configuration file
which holds their enter and exit banners, broadcast text colors, and
a short description (who banner). Users will like the ability to make
their broadcast colors unique.
(I) Invite Other Users
This will allow the user to invite users into the current area. Even
though this command will work in the lobby, it would not make much sence
to use.
(J) Join/Create Public/Private Areas
This will allow the user to join or create a new private or public area.
(T) Change Topic
This will allow the user to change the current area's topic of discussion
which is displayed in the list of areas (? at the join area prompt).
(P) Private Message
This will allow the user to broadcast private messages. However the
"*{user} {messagebody}" is a faster shortcut.
(U) List Users In Party Line
This will show a list of all user currently in the partyline and what
area they are in, if it is not a private area.
(O) OLM
This will do the same as the global menu command OLM, which allows the
user to send an Online Message.
(W) Who Online
This will do the same as the global menu command Who, which shows a list
of all users currently on the system.
PART 12 ONLINE PROGRAMS AREA
Trinity BBS uses AREXX for its online programs (games). This makes it
very easy for someone to create their own online programs. Trinity BBS is
already compatible with a large existing library of online games and
programs created with AREXX. Trinity BBS is 95% compatible with existing
Cnet Amiga and SkyLine BBS Arexx Pfiles. For most Cnet pfiles The only
modification that would be required is to replace pfiles: with OLP: in
filenames and paths. This can also be globally changed with an assignment
of pfiles: to olp: in your "BOOTBBS" script or startup sequence.
12.1 Online Program Commands
(A) Add
This command will allow the user (usually SYSOP) to add a new online
program to the list. Several questions will be asked at this point :
Will this Be A Directory?
If you selected YES the BBS will create a new directory of online
programs, which is a whole new list of online programs. This is
handy if you would like to have an area of utilities, adventure
games, and brain games.
File/Dir Name :
This is where you would enter the exact filename of the online
program (Example MastersEmpire) or a directory name (example :
Brain Games). Note: some AREXX programs have many seperate
programs or may require special command line arguements. If this
is true, you might have to create a small loader AREXX program
as the program to launch first and then spawn the required programs.
Description :
This is where you would describe the online program or directory.
Note : An * will be displayed on directory listings.
Access Level :
Enter an access level that is required to play or run this online
program. Note some online games include a maintance program which
you would require a SYSOP access level.
Credits Needed :
Enter the amount of OLP credits that are required to run the online
program or enter the directory. Note : You should not make a high
amount of credits just to enter a new directory since the online
programs that maybe included in this directory can have their own
required credits.
12.2 Using Online Programs In Text Files
Online Programs (AREXX SCRIPTS) may also be included in any text file
with the @#1filename@ parser command (See Parser Commands). These online
programs will run while displaying a text file, such as a last 10 users
program. This is usefull since Trinity BBS has the ability to add new
commands to some areas. These commands use text files which may run an
online program. See Adding And Editing Commands.
12.3 Supported AREXX Commands Used By Trinity BBS
Trinity BBS adds the following commands to AREXX. Please refer to
the AREXX User's Reference Manual for creating your own AREXX online
programs.
ADDCREDITS {number}
Adds given number of download credits to the user.
ADDPOINTS {number}
Adds given number of points (credits) to the user's OLP Credits.
ADDTIME {number}
Adds time to the user's remaining time, in minutes. Note : This
will not add time if auto maintenance is near.
ADDLEVEL {number}
Changes the users access level to the given number.
BAUD {number}
Set the current baud rate to {number}. This should not be used while
a connection is present.
BBSCOMMAND {char/string}
Will issue the given character that is one of the available global
commands. Note the user will require to have the priviledge set to use
some global commands. See Global Commands for more information.
BBSIDENTIFY {argument}
Returns the following for the given argument:
BBS Current Trinity BBS Version
EMULATION "ASCII" or "ANSI"
NAME Your BBS Name as in the main.config file
SYSOP The SYSOP's handle in the main.config file
TERM <baud> <columns> <rows> <lines>
USER "<username" "<callingfrom>" <access>
access wil be GUEST for new users, MEMBER
for other users and CO-SYSOP for if the
sysop menu priviledge is set and SYSOP for
account #1
BUFFERFLUSH
Flush serial input buffers if characters are remaining.
CALLEDITOR {number}
Involkes the Trinity Text Editor. The current contents of the
editor is loaded. The number parameter specifies the maximum number
of lines to input (it must not exceed 200). A "1" is returned if
the users chose "save" or a 0 if the user aborted.
CARRIERON
Tell Trinity to watch carrier status.
CARRIEROFF
Tell Trinity to stop checking for loss of carrier. Be carefull with
this command, it could easily lock the node if the carrier is lost and
no special use is made.
CHANGEWHAT {string}
Change the status field information in the node's status window,
the who list, and control's status window of the node.
CHANGEWHERE {string}
Same as CHANGEWHAT.
CHECKIO
Reports status of the carrier detect bit, returns 1 (TRUE) or
0 (FALSE).
CLEAREDITOR
Clears the contents of the editor buffer. Usefull before LOADEDITOR.
CLOSEDISPLAY
Closes the node's screen (puts the node in iconified mode)
CLS
Sends the clear screen code
DROPCARRIER
Will drop DTR of the serial port, hanging up the modem. You should not
use any input commands because Trinity will just send "###PANIC" because
the carrier is dropped.
EDIT {file}
Calls the Trinity Text editor using the default editor length given
by the EDLENGTH command and will safe the results of the edit to the
given filename. Returns 1 for success, any other result should be
considered a user abort.
EDLENGTH {number}
Changes the default max lines used by Trinity Text Editor to number.
The default is 200 lines.
FEEDBACK
Will send the user to the feedback routine of Trinity BBS.
FINDACCOUNT {string}
Trinity will search for the given handle or account number for a valid
user account. If a match is found the users account number will be
returned, otherwise a '0'.
GETCARRIER
Same as CHECKIO.
GETCHAR
Get one key/character from user.
GETNODEID {number}
Returns the address of the specific node data structure within the
nodebuf structure of the given node number. Returns -1 if node can
not be found.
GETPATH
Returns the current path location the Node is currently using. This
is usefull if the user is currently in a message area or a file area.
GETPORTID {number}
Same as GETNODEID.
GETUSER {number}
Used to pull various pieces of the users data into the Arexx program.
Where {number} equals :
0) Returns The Address To the NodeBuf Structure
1) User's Handle
2) User's Password
3) User's Real Name (First & Last)
4) User's City & State
5) User's Zip Code
6) User's Street Address
7) User's Time Remaining, In Minutes
8) Will return SYSOP COMMENT (used for compatibility)
9) User's Data Phone Number
10) User's Voice Phone Number
11) User's Last Call Date
12) Current Date & Time
13) Number of OLD E-Mail Messages Waiting
14) Number of NEW E-Mail Messages Waiting
15) User's Access Level
16) Access Group Name Description
17) Returns a 0, May Change In Future Versions
18) Minutes Used Today
19) Screen Clear Code - Returns 12 Always
20) Download Credits Remaining
21) OLP Credits Remaining
22) Total Calls To System (Current User)
23) Current Node
24) Current CPS (Baud Rate / 10, 2400 Baud would be 240cps)
25) UD Credit Ratio 1:n
26) Same As 25 for compatibility
27) Column Width (40 or 80)
28) Terminal Type 1 = ASCII, 2 = ANSI
29) Current Lines Per Page
30) Total Uploaded Kbytes
31) Total Uploaded Files
32) Total Downloaded Kbytes
33) Total Downloaded Files
34) Download File Limit Per Call
35) Same As 20 For Compatibility
36) Total Public Messages Left
37) Total E-Mail Messages Left
38) Who Banner (Description)
39) Presently Returns "UUCP" May Change
40) User's Account Number
41) Same as 41 For Compatibility
42) Bytes Uploaded This Call
43) Bytes Downloaded This Call
44) Files Uploaded This Call
45) Files Downloaded This Call
GETWHERE {number}
Returns the status string as displayed in the stats window from the
given node number.
HANGUP
Same as DROPCARRIER.
INLENGTH {number}
Changes the max number of charcters to input via a QUERY or RECIEVE
command. The default is 80 characters.
IREADY
Same as CHECKIO.
LOADEDITOR {path}
This will read the filename given by {path} into the editors buffer.
LOGENTRY {string}
Writes {string} into the caller log file.
LOGOFF
Forces the user off the BBS. This will display the logoff file first.
Note: The Arexx program should exit after this command.
MAYGETCHAR
Returns the waiting-input character or "NOCHAR" if the input buffer
is empty.
MCION
This turns on parser commands (default).
MCIOFF
This turns off parser commands.
NEWLINE
Returns the newline character.
OFFHOOK
Same as DROPCARRIER.
OPENDISPLAY
This will attempt to open the node's screen (un-iconify).
PRINT {string}
This will send {string} to the user including a cr/lf.
QUERY {string}
Prompts the user with {string} and will input a string up to the number
of chars specified by the INLENGTH command and return the result.
RECEIVE
Pauses for the user to input a line up to the number of chars specified
by the INLENGTH command and returns the result.
RESETMODEM
Sends the initialization strings to the modem and resets the
baud rate to the default port speed.
SAVEEDITOR {path}
Saves the contents of the editor buffer to the given filename.
SCREENOUT {string}
Outputs given string to the node's screen but not to the user (modem).
SENDFILE {path}
Displays the given text file.
SENDMODEM
Sends a string to the modem, but no to the screen.
SENDSTRING {string}
Sends given string to the user but without a cr/lf.
SEND {string}
Same as SENDSTRING.
SETMAILSUBJ {string}
Sets the subject of email before using writemail.
SETMAILFROM {string}
Sets who email is from before using writemail.
SETNODELOCATION
Same as CHANGEWHAT.
SETPROTOCOL {number}
Changes the default protocol from Zmodem to the given number as
if the user selected change protocol from a download or upload
prompt.
SPAWN {path}
Will start up a new AREXX process with a filename of {path}. The
program using this command most exit shortly afterwords
SYSOPLOG {string}
Same as LOGENTRY.
TRANSMIT {string}
Transmits string with a carriage return to the user. Same as PRINT.
VERSION
Returns the current version of Trinity BBS.
WRITEMAIL {string}
Writes the contents of the editor's buffer to the given users account
or handle. If handle or account number can not be found this command
will be ignored. Use FINDACCOUNT to safely make sure a user exists.
XDN {path}
Will send the specified path and filename to the user. The command
SETPROTOCOL should be used to select the protocol that will be used
for the transfer.
XUP {path}
Will receive the specified path and filename to the user. If a batch
upload protocol was used only the path need be sent. The command
SETPROTOCOL should be used to select the protocol that will be used
for the transfer.
EXIT
Always use EXIT to exit the arexx file.
Trinity BBS does not require an address command while running an
AREXX program or script. However, when used the arexx port for each node
is: "Trinity {node#}.Arexx". For example for node 1 the port would be
"Trinity 1.Arexx".
When a carrier is lost while arexx is running an online program,
Trinity BBS will send "###PANIC" to arexx (when using getchar, receieve, or
query). The online program should take this command and imediately exit
the online program. Otherwise, the online program may never stop even
though Trinity BBS has reset, causing a waste of valueable memory. Trinity
will try the "###PANIC" 10 times before giving up and sending the "HI" command
to AREXX and reseting. Due to the fact that this may lock your AREXX port,
you should not add any OLPs that do not check for this in some way.
NOTE: Trinity BBS does very little error checking with AREXX. Sending bad
values can crash your BBS, so be very carefull.
PART XX GLOBAL MENU
Trinity BBS includes a special menu set aside for global options.
These commands can be obtained by press '.' almost anywhere while online
the BBS, including reading messages, viewing file lists, every menu, etc.
xx.1 GLOBAL MENU COMMADS
The follow is a list of support global commands. These are mainly
for use with BBSs with multi-nodes. Some of these commands will require
that the user have the specified priviledge set. See Priviledges.
(T) Time
This command will give the user the amount of time he/she has
remaining this call.
(A) Avail
This command will allow the user to toggle her/her availabity to
Online Messages.
(W) Who
This command will display to the user a list of all users online all
nodes. The display will consist of handles, locations, status, and
whether they are available or not. If a user is hiding the node will
look as if it is waiting for a call. However, if the user has the
ability to see hidden users priviledge set, the users who are hiding
will be displayed normally but with an '*' next to their handle.
(M) Monitor
This command will toggle monitor mode on or off. When users logs on or
logs off (and is not hidden) a message will be displayed to all nodes
who have monitor mode on.
(H) Hide
This command will toggle hide from all nodes on or off. See the WHO
command above for more information.
(O) OLM
This command will allow the user to send an online message to any user
on any node as long as the user is not hidden (and the view hidden
priviledge is not set) and is available.
(S) Snoop
This command will allow the user (usually SySop) to snoop other nodes.
This will litterally display all information the user sees and does
on the node. This is very handy for remote SySops to watch users on
other nodes. Note: Node 0 or any node currently logged in locally
can not be snooped. If you attempt to snoop a node which has been
locally logged in, nothing will be displayed. Until a remote login
occurs. Also, do not attempt to snoop a node who is currently
snooping you, otherwise very strange effects will occur.
PART 13 PARSER COMMANDS
Trinity BBS uses parsar commands or commonly known as MCI commands in
text files, messages, and online programs. Parsar commands will slightly
slow down the output, but this is only noticable during a local call. For
this reason parser commands are turned off by default on text files. If you
wish to use parsar commands with text files, you must include a single
'CNTRL Y' and a return at the first line of the text file (See the text file
"Welcome.T280" for an example). If the 'CNTRL Y' is not found, all parser
commands will be displayed as they were entered. This speeds up high ANSI
incripted text files. By default parser commands are turned on while running
an arexx online program, but may be turned off by using the MCIOFF arexx
command. Parser commands may also be used in messages, news, and bulletins.
13.1 PARSER COMMAND LIST
Parser commands are initiated with a 'CNTRL Y'. For compatibility reasons
Trinity will also take 'CNTRL Q' as a parser initiater. If the initiater is
typed in the Trinity Text Editor an '@' will be displayed to the user because
CNTRL Y and CNTRL Q are not visible characters on some terminals. If you are
using parser commands within an external text editor, make sure it will allow
'CNTRL Y' to be keyed. Most external text editors on the Amiga will display
an arrow when 'CNTRL Y' is typed. To be visible in this documentation I will
use the '@' as the place maker for 'CNTRL Y'. In previous versions of
Trinity BBS the '@' was the initiater so please do not get confused, because
in version 2.0 the '@' will not work. There are three levels of parser
commands and they are: (Note: Again the @ represents a CNTRL Y for visual
purposes of this documentation ONLY)
LEVEL 1 PARSER COMMANDS:
@A1 = Do not allow abort of the text file and will display
More (Y/C)? at the more prompt without the 'N'
@A0 = Allow aborting of the text file
@Bn = Print n bells (beeps, chr(7))
@Cn = Change the characte color to n :
0 = Black 1 = Red 2 = Green 3 = Yellow
4 = Blue 5 = Magneta 6 = Cyan 7 = White
Colors 8,9,a,b,c,d,e,f are standard Amiga colors.
@F0 = Move cursor to home position.
@F1 = Move cursor to home position and clear screen.
@G1 = Wait For a Key Press.
@Hn = Print n number of backspaces.
@Nn = Print n number of carriage returns (lines).
@R1 = Set reverse printing on.
@R0 = Set reverse printing off.
@Zn = Change background color to n same colors as @Cn.
@^n = Move cursor up n lines.
@!n = Move cursor down n lines.
@>n = Move cursor to the right n spaces.
@<n = Move cursor to the left n spaces.
@-n = Insert n characters.
CNTRLYCNTRLY = Actually Display a CNTRL Y
CNTRLQCNTRLQ = Actually Display a CNTRL Q
LEVEL 2 PARSER COMMANDS:
@Vn = Display a system variable :
0 = Current date/time
1 = User's last call date/time
2 = User's handle
3 = User's real name
4 = User's Phone number
5 = User's password
6 = User's AccessGroup name
7 = Afternoon, Morning, or Evening depending on time
8 = Number of calls to the system
9 = User's Address
a = User's City and State
b = User's ZipCode or PostalCode
c = Time user has remaining
d = User's total calls to the system
e = Number of files user has downloaded
f = Number of files user has uploaded
g = Number of bytes user has downloaded
h = Number of bytes user has uploaded
i = Number of messages user has left
j = Time limit allowed per day
k = Calls allowed per day
l = Downloads allowed per call
m = Uploads allowed per call
n = UD Credit ratio
o = Messages allowed per call
p = E-Mail allowed per call
q = Time Used Today
r = Time Left This call
s = Total E-Mail Sent
t = Download Credits Left
u = OLP Credits Left
LEVEL 3 PARSER COMMANDS:
@*1{filename}@ = Display file with path/filename.
Never use in a text file or an arexx script that
was ran by a text file.
@#1{filename}@ = Run an AREXX online program from a text file
usefull for new commands.
@$1{filename}@ = Send an Amiga Dos Command.
Note: These level 3 parser commands may end with an '}' for compatibility
reasons. I tried to make Trinity BBS as compatible as possible with existing
AREXX pfiles, but some parser command modifications may be needed.
If you wish to allow your users to be able to use these parser commands
in their messages and email, you must set the proper priviledge setting for
each level. Of course, it is not wise to give any non-sysop user the
priviledge of level 3 commands or even level 2 commands.
Please expect more parser commands in future upgrades.
PART 14 EDITING AND ADDING NEW COMMANDS
Trinity BBS give the SYSOP the ability to change and add new commands
to the Main Menu, E-Mail Menu, Message Area Menu, File Transfer Area Menu,
SYSOP Options Menu, and the Partyline command menu. In the configuration
directory there should be command files for every menu and they are :
Note: Partyline's commands are handle a little different, please see
adding new commands to the partyline.
Commands.Main
This is the Main Menu commands.
Commands.Email
This is the E-Mail menu commands.
Commands.Msg
This is the Message Area Menu commands.
Commands.File
This is the File Transfer Area Menu commands.
Commands.Sysop
This is the SYSOP Options Menu commands.
Lets look at the Commands.Main for an example and how to edit and add
new commands :
G 'LogOff'
M 'Message Bases'
F 'File TransFers'
E 'Electronic Mail'
B 'Bulletins Or Text Files'
O 'Online Programs'
U 'UserLog List'
C 'Page SySop For Chat'
L 'Leave SySop FeedBack'
T 'Time Information'
P 'Edit Password'
$ 'Edit User Profile'
# 'Edit Terminal Params'
* 'Sysop Options Menu'
N 'Change New Item Date'
? '? = Future Commands
? 'Will Output File MainCommand.x
Y 'Your Status (Added Command)
?
?
?
?
?
?
?
You may change the actual command for any item, but you must keep it
in this order only. Going out of order will confuse the BBS. "?" are for
adding new commands (example the "Y" Your status (added command). Every
command file has 25 items, so you must include "?" for unused items.
14.1 Adding New Commands
To add new commands to a command file, just enter the letter or
character of the new command (you may include a remark or description of
the command for your records, see above) by replacing one of the "?" with
the new command. Next, you must create a text file for that command which
may and usually will include the parsar command "@#1{filename}@" to run an
AREXX online program. Note you do not need to include the "@" as the first
line on this text file as you do in most other text files, to tell the BBS
to expect parser commands since it already expects it for added commands.
The text filename for added commands is "MainCommand.x" for the Main Menu-
where "x" = the command character, "MsgCommand.x" for the Message Area
Menu, "FileCommand.x" for the File Area Menu, "EmailCommand.x" for the
E-Mail Area Menu, and "SysopCommand.x" for the SYSOP Options Menu.
14.2 Adding New Commands To Partyline
Adding new commands to the partyline is a little different then other
menu commands. The partyline does not have its own command description file
since partyline commands are hard coded and can not be changed. However,
new commands may be added. A new command for the partyline only requires
that the "PlineCommand.x" file be present in the configuration: directory.
For example to add a command 'Z' you would create the a text file named
"configuration:PlineCommand.Z". And then when ever a user types 'Z' at
the partyline command prompt that text file will be displayed running any
arexx programs you may have included. You would want to include the
description of this command in the "text:HELP-PLINE" file.
